Versions:
nsc, the Namespace CLI, is an open-source command-line interface published by Namespace Labs, Inc. for Namespace's developer-optimized cloud compute platform. The tool enables developers and engineering teams to manage Namespace compute, builds, containers, caches, and cloud resources directly from the terminal, and it is equally suited to interactive local use and automated CI workflows. With nsc, users can provision and manage ephemeral compute instances on demand, making it practical to spin up short-lived environments for development, testing, and build execution without manual infrastructure work. The CLI supports connecting to running instances through SSH, VNC, or RDP, giving users flexible remote access options depending on whether they need a shell session or a graphical desktop. It also handles container-oriented workflows, allowing users to run and build container workloads, and it provides commands to configure Kubernetes access for clusters managed through the platform. Beyond compute and containers, nsc covers a broad range of supporting platform resources: users can manage caches and artifacts to speed up builds, interact with container registries, handle secrets and authentication, and administer other Namespace resources from a single terminal-based tool. This breadth of functionality positions nsc within the developer tools and cloud management category, specifically as an infrastructure and platform CLI for teams building, testing, and deploying software on cloud compute. The current version of nsc is 0.0.569, and the catalog lists four versions of the software in total, indicating an actively maintained release history. Because it is open source, the CLI can be inspected and integrated into existing developer environments, and its design for both terminal sessions and CI pipelines makes it a unified control point for the full Namespace platform, covering the workflow from provisioning compute and building containers through to managing the secrets, caches, and registries that those workloads depend on.
Tags: